Cache reset poses so effectTargets maintain position #117
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the effectTargets are moved after the application is running when OnColliderEventPressUp restores the positions from resetPoses back into the effectTargets they'll get restored back to their original position in the scene instead of their updated positions. Called CacheResetPoses() from OnColliderEventPressEnter to update the cache so the restore works properly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the effectTargets are moved after the application is running when OnColliderEventPressUp restores the positions from resetPoses back into the effectTargets they'll get restored back to their original position in the scene instead of their updated positions. Called CacheResetPoses() from OnColliderEventPressEnter to update the cache so the restore works properly.
This is an additional fix to issue #114.